Skip to content

Conversation

graeme-a-stewart
Copy link
Member

I revised the project affiliation pages removing the gold/sliver/bronze levels.

A new HSF Project badge (grey/red) has been generated.

So as to not lose the work embodied in the previous levels I reinterpreted these in the framework of the ARDC/EVERSE 3-tier model of software. The RFC language (SHOULD/MUST) was toned down.

N.B. the link checker will fail because the cached badge link will not exist until this PR is accepted.

Generate a "plain" HSF Project badge, in grey and red.

Remove the table entries for old badges (bronze, silver, gold).
The old cached badges are not removed.
Remove gold/silver/bronze project levels.

Rewrite advice and guidelines referring to the 3-tier
software model.
Copy link

netlify bot commented Jul 9, 2025

Deploy Preview for earnest-hotteok-b1e1bf ready!

Name Link
🔨 Latest commit f798673
🔍 Latest deploy log https://app.netlify.com/projects/earnest-hotteok-b1e1bf/deploys/6874f7bc19dc0000086c8f9e
😎 Deploy Preview https://deploy-preview-1746--earnest-hotteok-b1e1bf.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@graeme-a-stewart graeme-a-stewart marked this pull request as draft July 9, 2025 14:28
@eduardo-rodrigues
Copy link
Member

Hi @graeme-a-stewart, brilliant that you found time so quickly to move this important rework forward 👍!

I will read it asap. Just a couple of things for now:

  • We brainstormed at some point on the idea of having scoped badges in the future for documentation, testing, you name it. Are you suggesting by using the singular "Badge" that we will move forward with a single badge and will drop this idea?
  • The badge is listed as "HSF Affiliate" but says "HSF Project". We should be consistent and the former seems better, no?

graeme-a-stewart and others added 3 commits July 10, 2025 11:59
Co-authored-by: Eduardo Rodrigues <[email protected]>
Co-authored-by: Eduardo Rodrigues <[email protected]>
Co-authored-by: Eduardo Rodrigues <[email protected]>
Copy link
Member

@eduardo-rodrigues eduardo-rodrigues left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi again @graeme-a-stewart, excellent rework. I like it a lot 👍 !

I left a few trivial suggestions. See if you fancy or not the change.

Let's discuss this at the SG meeting this afternoon.

@graeme-a-stewart
Copy link
Member Author

Hi @graeme-a-stewart, brilliant that you found time so quickly to move this important rework forward 👍!

I will read it asap. Just a couple of things for now:

  • We brainstormed at some point on the idea of having scoped badges in the future for documentation, testing, you name it. Are you suggesting by using the singular "Badge" that we will move forward with a single badge and will drop this idea?

I think the multiple badges idea is interesting, but quite inchoate and I don't know what to propose for it specifically. Then a whole set of criteria would need to be developed as well.

So my thought was start basic, simple affiliation for now, and develop from here, as the need or desire arises.

  • The badge is listed as "HSF Affiliate" but says "HSF Project". We should be consistent and the former seems better, no?

Yes! I agree. "HSF Affiliate" or "HSF Affiliated"?

@eduardo-rodrigues
Copy link
Member

I totally agree. Best to start simple and solid.

You're the native speaker but my naive thought was "HSF Affiliated" as in "affiliated to".

@graeme-a-stewart
Copy link
Member Author

I totally agree. Best to start simple and solid.

You're the native speaker but my naive thought was "HSF Affiliated" as in "affiliated to".

I also prefer "HSF Affiliated" (adjective) over "HSF Affiliate" (noun).

Copy link
Member

@eduardo-rodrigues eduardo-rodrigues left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's give a bit of time for others to look but I'm happy with this. Approving and it can be moved from Draft to Ready IMO.

@eduardo-rodrigues eduardo-rodrigues marked this pull request as ready for review July 14, 2025 10:10
@eduardo-rodrigues
Copy link
Member

There was broad consensus within the Steering Group that this is a very nice improvement 👍. Merging.

@eduardo-rodrigues eduardo-rodrigues merged commit ca303a8 into main Jul 16, 2025
7 of 9 checks passed
@eduardo-rodrigues eduardo-rodrigues deleted the revise-project-affiliation branch July 16, 2025 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants